View Issue Details

IDProjectCategoryView StatusLast Update
0001681T99X171.00 SKB EagleSW Issuepublic2025-04-07 10:02
Reporter(ALTech) Younkwang Jung Assigned To(SW) Kerwin Chen Due Date2023-03-17 16:24
PrioritynormalSeveritys4-minorReproducibilityhave not tried
Status closedResolutionnot a bug 
Summary0001681: [Smart3][ATV12] BA01 BT disconnect issue
DescriptionHi Kerwin

JIRA is
https://jira.skbroadband.com/browse/FSTB12-89

[ issue ]
Disconnect issue occur when connecting RCU to STB using BT

[ Reproduction step ]
1. BA01 RCU BT Pairing (* + #)

[ Expected Results ]
It should be connected continuously without disconnection

[ test results ]
BT is Connected and disconnected after approximately 1 minute
- BMM /BRM Same

Please check it
Thank you
YK.Jung=
TagsNo tags attached.
Attach Tags

Users monitoring this issue

User List (ALTech) JunGyu Kim , (ALTech) SY Yoon

Activities

(ALTech) Younkwang Jung

2023-03-16 15:26

developer  

FSTB12-89.zip (1,948,705 bytes)

(SW) Kerwin Chen

2023-03-17 11:53

developer   ~0012565

Last edited: 2023-03-17 12:02

Hi YK,

From the log, it seems SKB was doing RCU repairing tests.
There are several pairing messages in log file.
And they also used 2 different RCU to do the RCU pairing. (BRM_BA01_0D2, BRM_BA01_AD3)
I see there are some pairing errors with code 33. (can't find RCU device)
As I remember, it may be due to there are too many BT devices in the environment.
BTW, sometimes it is failed due to RCU doesn't enter pairing mode.

02-17 15:32:42.827 7177 7177 I BtvBtPairingService: BT startScanning controlState = 1
..
02-17 15:34:18.432 7177 7177 I BtvBtPairingService: BT startScanning controlState = 0
..
02-17 15:34:38.758 4776 4776 D MainActivity: remote intent function : pairing, device_name : , status : fail, reason : scan[33]
..
02-17 15:36:57.869 7177 7177 I BtvBtPairingService: BT startScanning controlState = 0
..
02-17 15:43:28.288 7177 7177 I BtvBtPairingService: BT startScanning controlState = 0
..
02-17 15:43:48.585 7177 7177 E BtvBtPairingService: sendBroadcastNaviLog action : com.skbb.intent.navilog.bluetoothrcu, function = pairing, state = fail, reason = scan[33], name =
..
02-17 15:43:53.626 7177 7177 I BtvBtPairingService: BT startScanning controlState = 0
..
02-17 15:44:13.935 7177 7177 E BtvBtPairingService: sendBroadcastNaviLog action : com.skbb.intent.navilog.bluetoothrcu, function = pairing, state = fail, reason = scan[33], name =
..
02-17 15:45:27.059 7177 7177 I BtvBtPairingService: BT startScanning controlState = 0
..
02-17 15:45:47.353 7177 7177 E BtvBtPairingService: sendBroadcastNaviLog action : com.skbb.intent.navilog.bluetoothrcu, function = pairing, state = fail, reason = scan[33], name =
..
02-17 15:46:06.341 7177 7177 I BtvBtPairingService: BT startScanning controlState = 0
..
02-17 15:46:20.975 7177 7177 D BtvBtPairingService: BT onProfileConnectionStateChanged audio pairing ok handler

(ALTech) Younkwang Jung

2023-03-20 09:25

developer   ~0012571

Hi Kerwin

How can I check whether the RCU has entered pairing mode or not?

Thank you
YK.Jung

(SW) Kerwin Chen

2023-03-20 09:55

developer   ~0012572

Hi YK,

RCU pairing is controlled by SPTEK's application (BtvBtPairingService).
I think "BT startScanning" is where the application starts to do RCU pairing.
You can check it with SPTEK for more details.

Thank you !

(SW) Kerwin Chen

2025-04-07 10:02

developer   ~0017421

no activity for this issue

Issue History

Date Modified Username Field Change
2023-03-16 15:26 (ALTech) Younkwang Jung New Issue
2023-03-16 15:26 (ALTech) Younkwang Jung Status new => assigned
2023-03-16 15:26 (ALTech) Younkwang Jung Assigned To => (SW) Kerwin Chen
2023-03-16 15:26 (ALTech) Younkwang Jung File Added: FSTB12-89.zip
2023-03-16 15:27 (ALTech) Younkwang Jung Issue Monitored: (ALTech) SY Yoon
2023-03-16 15:27 (ALTech) Younkwang Jung Issue Monitored: (ALTech) JunGyu Kim
2023-03-17 11:53 (SW) Kerwin Chen Note Added: 0012565
2023-03-17 12:02 (SW) Kerwin Chen Note Edited: 0012565
2023-03-20 09:25 (ALTech) Younkwang Jung Note Added: 0012571
2023-03-20 09:55 (SW) Kerwin Chen Note Added: 0012572
2025-04-07 10:02 (SW) Kerwin Chen Status assigned => closed
2025-04-07 10:02 (SW) Kerwin Chen Resolution open => not a bug
2025-04-07 10:02 (SW) Kerwin Chen Note Added: 0017421